Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(cli): avoid false positive cli upgrade suggestions #12497

Merged
merged 1 commit into from
Jan 31, 2025

Conversation

hsheth2
Copy link
Collaborator

@hsheth2 hsheth2 commented Jan 30, 2025

Skips yanked releases when determining the latest CLI release. This is necessary because we previously released and yanked a 15.0.4 release.

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Skips yanked releases when determining the latest CLI release.
This is necessary because we previously released and yanked a 15.0.4
release.
@github-actions github-actions bot added the ingestion PR or Issue related to the ingestion of metadata label Jan 30, 2025
Copy link

codecov bot commented Jan 30, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Files with missing lines Coverage Δ
metadata-ingestion/src/datahub/upgrade/upgrade.py 62.27% <100.00%> (+0.17%) ⬆️

... and 4 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 280e82a...474af3f. Read the comment docs.

@sgomezvillamor
Copy link
Contributor

Some package versions in pypi.org are marked as yanked, which communicates to the package installer (such as pip) that the version should not be installed unless it is the only one that matches a version specifier (using either == or === ).

After reviewing some of the yanked versions in https://pypi.org/pypi/acryl_datahub/json, wondering why not removing some of them such as 15.0.4?

@datahub-cyborg datahub-cyborg bot added pending-submitter-response Issue/request has been reviewed but requires a response from the submitter and removed needs-review Label for PRs that need review from a maintainer. labels Jan 31, 2025
filtered_releases = {
version: release_files
for version, release_files in releases.items()
if not all(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not all or not any ? 🤔

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have two files per release - a .tar.gz and .whl file. If in the future we add architecture-specific .whl files, we'll have multiple. We should only really consider a release yanked if every file is yanked - if we yank only a specific file due to a packaging issue, the release is still mostly valid

@datahub-cyborg datahub-cyborg bot added pending-submitter-merge and removed pending-submitter-response Issue/request has been reviewed but requires a response from the submitter labels Jan 31, 2025
@hsheth2 hsheth2 merged commit 317b740 into master Jan 31, 2025
243 of 276 checks passed
@hsheth2 hsheth2 deleted the ignore-bad-pypi-release branch January 31, 2025 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ingestion PR or Issue related to the ingestion of metadata pending-submitter-merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants